Skip to content

fix: bump package.json version on semantic release - #7

Merged
Peyton-Spencer merged 2 commits into
mainfrom
fix/release-version-bump
May 3, 2026
Merged

fix: bump package.json version on semantic release#7
Peyton-Spencer merged 2 commits into
mainfrom
fix/release-version-bump

Conversation

@Peyton-Spencer

@Peyton-Spencer Peyton-Spencer commented Mar 18, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Contributor

Summary

  • Add @semantic-release/git plugin to .releaserc.json so the version bump in package.json is committed back to main after each release
  • Add @semantic-release/git ^12.0.0 to devDependencies
  • Plugin is placed last in the plugins array (after npm publish and GitHub release) per semantic-release's recommended ordering

Problem

The current semantic-release config creates GitHub releases and publishes to npm, but never commits the updated package.json version back to the repo. This means package.json stays at 0.1.0 on main regardless of the actual published version.

Test plan

  • Verify .releaserc.json is valid JSON with correct plugin order
  • Verify @semantic-release/git is in devDependencies
  • Next release should commit the version bump with chore(release): <version> [skip ci]

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Improved the release automation pipeline with enhanced Git asset management and standardized commit messaging for more consistent version control history.

@Peyton-Spencer @claude
fix: add @semantic-release/git to bump package.json on release
4ad1e49 
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Mar 18, 2026 •
edited
Loading

Copy link
Copy Markdown

Warning

Rate limit exceeded

@Peyton-Spencer has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 4 minutes and 52 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 323a4070-e956-4b69-bd16-b9eb93e1b333

📥 Commits

Reviewing files that changed from the base of the PR and between 4ad1e49 and c609baf.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • package.json
📝 Walkthrough

Walkthrough

Adds semantic-release git plugin configuration with assets management and commit message formatting to the release pipeline. Introduces a corresponding devDependency to enable automated Git operations during version releases.

Changes

Cohort / File(s) Summary
Release Configuration
.releaserc.json		 Added @semantic-release/git plugin block with asset tracking (package.json) and standardized release commit message format including version and release notes.
Project Dependencies
package.json		 Added @semantic-release/git@^12.0.0 to devDependencies to support Git asset management and versioning in the release pipeline.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰✨ A nimble hop through release automation,
Git assets tracked with precision and care,
Version bumps committed with semantic notation,
Our burrow's release process, smooth as air! 🚀

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'fix: bump package.json version on semantic release' directly describes the main change: configuring semantic-release to commit version bumps back to the repository via the git plugin.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/release-version-bump

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
Review rate limit: 0/1 reviews remaining, refill in 4 minutes and 52 seconds.

Comment @coderabbitai help to get the list of available commands and usage tips.

@Peyton-Spencer @codex
fix: use published semantic-release git version
c609baf 
Co-Authored-By: Codex <noreply@openai.com>
@Peyton-Spencer
Peyton-Spencer merged commit 70fd1c6 into main May 3, 2026
2 checks passed
@Peyton-Spencer
Peyton-Spencer deleted the fix/release-version-bump branch May 3, 2026 22:11
github-actions Bot pushed a commit that referenced this pull request May 3, 2026
@semantic-release-bot
chore(release): 1.1.2 [skip ci]
05efd46 
## [1.1.2](v1.1.1...v1.1.2) (2026-05-03)

### Bug Fixes

* bump package.json version on semantic release ([#7](#7)) ([70fd1c6](70fd1c6))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Peyton-Spencer